Methods, systems, and computer readable media for providing mapping information associated with port control protocol (pcp) in a test environment

ABSTRACT

Methods, systems, and computer readable media for a testing platform involving application traffic are disclosed. According to one method, the method occurs at a testing platform including an emulated port control protocol (PCP) client module for requesting public network addressing information for an emulated application server module and an emulated application client module for sending application traffic. The method includes receiving, from a device under test (DUT), the public network addressing information in response to a PCP request. The method also includes providing mapping information to the emulated application client module, wherein the mapping information includes the public network addressing information.

PRIORITY CLAIM

This application claims the benefit of Romanian Patent Application No.A/00674-2012, filed Sep. 21, 2012; the disclosure of which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

The subject matter described herein relates to network equipmenttesting. More specifically, the subject matter relates to methods,systems, and computer readable media for providing mapping informationassociated with PCP in a test environment.

BACKGROUND

In some communications networks, user devices (e.g., smartphones,computers, mobile handsets, or other user equipment (UE)) may act asapplication clients by requesting information from one or moreapplication servers. Some application servers may be located in aprivate network or environment. As such, these application servers maycommunicate with application clients (e.g., user devices) in othernetworks, such as the Internet, via a network address translator (NAT),a firewall, a customer premise equipment (CPE) router, or a proxyserver.

Conventionally, application servers send keep alive traffic to firewallsor NATs so that ports on these devices remain open for receivingincoming traffic. For example, a firewall may be configured to keep aport open if a message is received every few minutes. In this example,an application server may frequently send messages to guarantee that theport is open for incoming traffic from application clients.

Port control protocol (PCP), which is currently under heavy development,is intended to enable application servers to run in private environments(e.g., behind a NAT). PCP is discussed in an IETF draft documententitled “Port Control Protocol (PCP) draft-ietf-pcp-base-26d” datedJun. 5, 2012, the disclosure of which is incorporated by referenceherein in its entirety. PCP can be used to control how incoming packetsare forwarded by upstream devices, such as a NAT or a firewall, and toreduce and optimize keep alive traffic. For example, a PCP clientcomponent may be communicatively coupled to an application server, suchas a web server or a hypertext transfer protocol (HTTP) server. A PCPserver component may be communicatively coupled to a firewall or a NAT.Using PCP signaling between the PCP client and PCP server, anapplication server may negotiate a public IP and port for receivingincoming traffic via the NAT or firewall. Using PCP-negotiatedinformation, the firewall or NAT is capable of sending incomingapplication traffic to the application server and sending outgoingapplication traffic from the application server.

While PCP may be useful in facilitating communication betweenapplication clients and an application server behind a NAT or afirewall, network equipment simulation and/or testing platforms addfurther complexity. For example, to properly test a PCP-controllabledevice, a testing platform may be capable of simulating or emulating aPCP client component, an application server, one or more applicationclients, and related signaling between such components and the networkequipment being tested.

Accordingly, in light of these difficulties, a need exists for methods,systems, and computer readable media for providing mapping informationassociated with PCP in a test environment.

SUMMARY

Methods, systems, and computer readable media for providing mappinginformation associated with PCP in a test environment are disclosed.According to one method, the method occurs at a testing platformincluding an emulated port control protocol (PCP) client module forrequesting public network addressing information for an emulatedapplication server module and an emulated application client module forsending application traffic. The method includes receiving, from adevice under test (DUT), the public network addressing information inresponse to a PCP request. The method also includes providing mappinginformation to the emulated application client module, wherein themapping information includes the public network addressing information.

A system for providing mapping information associated with PCP in a testenvironment is also disclosed. The system includes an emulatedapplication client module configured to send application traffic. Thesystem also includes an emulated port control protocol (PCP) clientmodule configured to request public network addressing information foran emulated application server module, wherein the emulated port controlprotocol (PCP) client module is further configured to receive, from adevice under test (DUT), the public network addressing information inresponse to a PCP request, and to provide mapping information to theemulated application client module for use in sending applicationtraffic, wherein the mapping information includes the public networkaddressing information.

The subject matter described herein may be implemented in software incombination with hardware and/or firmware. For example, the subjectmatter described herein may be implemented in software executed by aprocessor (e.g., a hardware-based processor). In one exemplaryimplementation, the subject matter described herein may be implementedusing a non-transitory computer readable medium having stored thereoncomputer executable instructions that when executed by the processor ofa computer control the computer to perform steps. Exemplary computerreadable media suitable for implementing the subject matter describedherein include non-transitory devices, such as disk memory devices, chipmemory devices, programmable logic devices, such as field programmablegate arrays, and application specific integrated circuits. In addition,a computer readable medium that implements the subject matter describedherein may be located on a single device or computing platform or may bedistributed across multiple devices or computing platforms.

As used herein, the term “node” refers to a physical computing platformincluding one or more processors and memory.

As used herein, the terms “function” or “module” refer to software incombination with hardware and/or firmware for implementing featuresdescribed herein. In some embodiments, a module may include afield-programmable gateway array (FPGA), an application-specificintegrated circuit (ASIC), or a processor.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter described herein will now be explained with referenceto the accompanying drawings of which:

FIG. 1 is a diagram illustrating an exemplary communications scenarioinvolving an application server in a private network and an applicationclient in a public network;

FIG. 2 is a diagram illustrating a test system according to anembodiment of the subject matter described herein;

FIG. 3 is a diagram illustrating providing mapping information via aninternal connection according to an embodiment of the subject matterdescribed herein;

FIG. 4 is a diagram illustrating providing mapping information via anexternal connection according to an embodiment of the subject matterdescribed herein;

FIG. 5 is a diagram illustrating providing mapping information viashared data storage according to an embodiment of the subject matterdescribed herein;

FIG. 6 is a diagram illustrating providing mapping information via awireless connection according to an embodiment of the subject matterdescribed herein; and

FIG. 7 is a diagram illustrating an exemplary process for providingmapping information associated with PCP in a test environment accordingto an embodiment of the subject matter described herein.

DETAILED DESCRIPTION

The subject matter described herein discloses methods, systems, andcomputer readable media for providing mapping information associatedwith PCP in a test environment. PCP may allow hosts to operate serversfor a long time (e.g., a webcam) or a short time (e.g., while playing agame or on a phone call) when behind a NAT, including when behind acarrier-grade NAT (CGN) operated by an Internet service provider or anIPv6 firewall integrated in an CPE router. In particular, PCP may allowapplications to create mapping information. The mapping information mayinclude an association between an external or public IP address,protocol, and/or port and an internal or private IP address, protocol,and port. A NAT or a firewall may use the mapping information to forwardor route inbound communications from public network that are destinedfor application servers in private networks.

When testing scenarios involving PCP, it may be desirable to test adevice (e.g., a NAT and/or a firewall) under non-trivial loadconditions. One significant challenge with respect to such a testingscenario is the need to make the application traffic go from theemulated application client, through a public address, to the emulatedapplication server via the device under testing (DUT), where the publicaddress is negotiated or learned through the use of PCP signalingbetween an emulated PCP client and an emulated PCP server. However, themechanism by which the application client obtains knowledge of thePCP-negotiated public address is beyond the scope of the PCP protocol.

Advantageously, aspects of the present subject matter herein may includea test system configured to provide mapping information associated withPCP in a test environment. For example, in a test system, an emulatedapplication client may receive mapping information about one or moreemulated application servers. The emulated application client may usethe mapping information in generating or modifying packets such that theDUT receives application traffic addressed to one or more public IPaddresses and/or port numbers associated with the emulated applicationservers. For example, the DUT may receive application traffic addressedto public IP addresses and/or port numbers, may modify the packets sothat the packets are addressed to private IP addresses and/or portnumbers associated with the public IP addresses and/or port numbers, androute the application traffic to the application servers identified bythe private IP addresses and/or port numbers.

FIG. 1 is a diagram illustrating an exemplary communications scenarioinvolving an application server in a private network and an applicationclient in a public network. Referring to FIG. 1, a network element 104may be associated with a public network 100 and a private network 102.Network element 104 may be any suitable entity for providing orimplementing NAT functionality and/or port control functionality. Forexample, network element 104 may include any PCP-controllable device,such as a CGN, a small NAT (e.g., a residential NAT), a router (e.g., anInternet protocol version 6 (IPv6) router, an IP version 4 (IPv4)router, and a dual-stack router), a proxy server, or a firewall.

Network element 104 may include a firewall and/or NAT (Firewall/NAT)module 106 and a PCP server module (PSM) 108. Firewall/NAT module 106may be any suitable entity (e.g., software executing on a processor)that provides filtering, NAT functionality, and/or port controlfunctionality. For example, Firewall/NAT module 106 may control ormodify packet flows so as to communicate packets between entities indifferent networks.

PSM 108 may be any suitable entity (e.g., software executing on aprocessor) for interacting with a PCP client, a PCP-controllable device,and/or related modules. For example, PSM 108 may communicate with a PCM116 to determine an appropriate mapping which may be used to configurethe PCP-controllable device. In some embodiments, PSM 108 may manageaddress mapping and/or port control on network element 104. By managingaddress mapping, the PCP-controllable device may implement policies orflow rules to accept application traffic addressed to certaindestinations and forward the traffic to associated private addresses.

Network element 104 may communicate with various nodes in public network100, such as an application client 110. Application client 110 may beany suitable entity for requesting application data or traffic from anapplication server. For example, an application client 110 may be amobile phone or computing device, or a software component (e.g., a webbrowser) therein.

Network element 104 may also communicate with various nodes in privatenetwork 102, such as a host 112. Host 112 may be any suitable entity(e.g., a web server) for communicating with network element 104. Forexample, host 112 may a computing platform or other system. Host 112 mayinclude an application server module (ASM) 114 and a PCP client module(PCM) 116. ASM 114 may be any suitable entity (e.g., software executingon a processor) configured to handle requests for application trafficfrom one or more application clients 110.

PCM 116 may be any suitable entity (e.g., software executing on aprocessor) for interacting with a PCP server, an application server,and/or related modules. For example, PCM 116 may communicate with a PSM108 to request mapping information, such as a public IP address and/orport number. During PCP signaling, one or more private addresses and/orport numbers associated with ASM 114 or host 112 may be provided to PSM108. PSM 108 may determine a public IP address, protocol (e.g., IPv6,IPv4, or both), and/or port number for reaching host 112 (e.g., viapublic network 100) and may send mapping information to PCM 116. Forexample, a PCP server response (e.g., a notification message) may beself-describing and complete. The response may include mappings orassociations of internal (private) and external (public) addresses,protocol, and/or ports and a lifetime associated with the mapping. Thelifetime may be used to indicate how long a public IP address will beassociated with a private IP address and/or how long firewall/NAT module106 will continue to map traffic between the addresses.

After a public IP address, protocol, and/or port number is negotiated ordetermined, remote computers may be informed about the public IPaddress, protocol, and/or port number. However, it is important to notethat PCP does not provide a rendezvous function to inform remotecomputers. As such, another signaling mechanism is used to inform remotecomputers (e.g., application client 110) about the public IP address,protocol, and/or port number for connecting to host 112. For example,additional devices, such as a rendezvous server, a SIP proxy server, ora domain name service (DNS) server, and various protocols may berequired to inform application client 110.

After application client 110 is informed of the public IP address,protocol, and/or port number via another signaling mechanism,application client 110 may send application traffic (e.g., HTTPrequests) addressed to the public IP address, protocol, and/or portnumber. Network element 104 and/or Firewall/NAT module 106 may receivethe application traffic, modify the traffic using stored mappinginformation, and forward the traffic towards host 112. For example,after receiving a packet from application client 110, Firewall/NATmodule 106 may modify a destination address pointing to a public IPaddress in the received packet to a private IP address associated withhost 112. After modification, Firewall/NAT module 106 may send thepacket to host 112 and/or ASM 114 for further processing.

After receiving and processing requests from application client 110,host 112 and/or ASM 114 may respond by providing application data orother information. For example, an HTTP or IP response packet may beaddressed to application client 110 and include a source addressassociated with a private IP address identifying host 112. Networkelement 104 and/or Firewall/NAT module 106 may receive the applicationtraffic, modify the traffic using stored mapping information, andforward the traffic towards application client 110. The traffic receivedby application client 110 may include a source address associated with apublic IP address IP address identifying host 112.

FIG. 2 is a diagram illustrating a test system according to anembodiment of the subject matter described herein. In the embodimentshown in FIG. 2, a test system 206 may include various modules fortesting a PCP-controllable device or DUT 200, such as a network routeror proxy server with firewall and/or NAT functionality. In someembodiments, test system 206 may be configured to test the ability ofDUT 200 to communicate or route application traffic between anapplication server in a private network and an application client in apublic network.

In some embodiments, test system 206 may be configured to simulate oremulate some or all of the following: an application server and anassociated PCP client, and an application client. For example, asillustrated in FIG. 2, test system 206 may include communications module1 (CM1) 208 and communications module 2 (CM2) 214. CM1 208 and CM2 214may each be any suitable entity for communicating with a DUT 200. Forexample, CM1 208 may include one or more network interface cards (NICs)having one or more physical or virtual ports for receiving messages fromor sending messages to DUT 200.

In some embodiments, CM1 208 and CM2 214 may include additional modules,such as emulated ASM (EASM) 210 and emulated PCM (EPCM) 212, and/oremulated ACM (EACM) 216. In some embodiments, modules in test system 206may be configured differently, such as each module being separate orsome modules being combined.

In some embodiments, CM1 208 and CM2 214 may be implemented using thesame or different hardware or resources. For example, CM1 208 may beassociated with a first processor, blade, or card and CM2 214 may beassociated with a second processor, blade, or card. In another example,CM1 208 and CM2 214 may both be associated with a first processor,blade, or card.

EASM 210, EPCM 212, and EACM 216 may include similar functionality asdescribed above in regard to ASM 114, PCM 116, and application client110, respectively. For example, EASM 210 may be configured to handlerequests for application traffic from EACM 216, EPCM 212 may beconfigured to interact with PSM 108 and EASM 210, and EACM 216 may beconfigured to generate requests for application data or traffic fromEASM 210.

As indicated above, one significant challenge with respect to thetesting scenario in FIG. 2 is that EACM 216 must somehow gain knowledgeof the public network addressing information that has been negotiated byEPCM 212, but the mechanism by which an application client obtainsknowledge of the PCP-negotiated public address of DUT 200 is beyond thescope of the PCP protocol.

In accordance with aspects of the present subject matter, mappinginformation, such as a PCP-negotiated public address of DUT 200associated with EASM 210, may be distributed internally within testsystem 206. For example, test system 206 may include functionality forproviding mapping information from EPCM 212 to EACM 216. In thisexample, by internally providing mapping information (e.g., a public IPaddress and port number) to EACM 216, testing of DUT 200 may beself-contained without requiring additional external resources (e.g., aDNS server) to provide public network addressing information to EACM216.

In response to providing mapping information to EACM 216, EACM 216 maybe configured to modify or generate packets destined to EASM 210. Forexample, EACM 216 may be preconfigured with or otherwise be aware ofprivate network addressing information (e.g., a private IP address andport number) associated with EASM 210. In this example, EACM 216 maygenerate packets addressed to EASM 210 using the private networkaddressing information. However, prior to sending the packets to DUT200, EACM 216, or another module, may modify the packets usingassociated public network addressing information obtained from thereceived mapping information. In another example, EACM 216 may generatepackets addressed to EASM 210 using the public network addressinginformation obtained from the received mapping information.

DUT 200 may receive packets from EACM 216. The packets may includepublic network addressing information associated with EASM 210. Usingmapping information stored at DUT 200, DUT 200 may determine privatenetwork addressing information associated with EASM 210, modify thepackets to include the private network addressing information, and sendthe packets to EASM 210.

FIG. 3 is a diagram illustrating providing mapping information via aninternal connection according to an embodiment of the subject matterdescribed herein. In the embodiment shown in FIG. 3, CM1 208 and CM2 214may be co-located within test system 206 and may be communicativelycoupled via an internal connection 300. In some embodiments, test system206 may include one or more hardware platforms or chassis. For example,a first processor blade may be configured as CM1 208 and a secondprocessor blade may be configured as CM2 214. The first and secondprocessor blades may be associated with the same or different hardwareplatforms or chassis.

In some embodiments, communications between CM1 208 and CM2 214 may befacilitated by an internal connection, such as a backplane connection ora mid-plane connection. For example, in a test system 206 where bladesare part of a same platform or chassis, mapping information (e.g., apublic IP address and port number for reaching EASM 210) may be sent viaan internal communication network or bus, such as an Ethernet fabric ora serial communication bus.

FIG. 4 is a diagram illustrating providing mapping information via anexternal connection according to an embodiment of the subject matterdescribed herein. In the embodiment shown in FIG. 4, CM1 208 and CM2 214may be co-located within test system 206 and may be communicativelycoupled via an external connection 400. In some embodiments, test system206 may include one or more hardware platforms or chassis. For example,a first processor blade may be configured as CM1 208 and a secondprocessor blade may be configured as CM2 214. The first and secondprocessor blades may be associated with the same or different hardwareplatforms or chassis.

In some embodiments, communications between CM1 208 and CM2 214 may befacilitated by an external connection 400, such as an external cableconnection. For example, mapping information may be sent via a serialinterface cable, such as a fibre channel (FC) cable.

FIG. 5 is a diagram illustrating providing mapping information viashared data storage according to an embodiment of the subject matterdescribed herein. In the embodiment shown in FIG. 5, CM1 208 and CM2 214may be co-located within test system 206 and may be communicativelycoupled via shared data storage 500. In some embodiments, test system206 may include one or more hardware platforms or chassis. For example,a first processor blade may be configured as CM1 208 and a secondprocessor blade may be configured as CM2 214. The first and secondprocessor blades may be associated with the same or different hardwareplatforms or chassis.

In some embodiments, communications between CM1 208 and CM2 214 may befacilitated by a shared data storage 500 that is internal to oraccessible by test system 206, or portions therein. Exemplary shareddata storage modules may include random access memory, magnetic storagemedia (e.g., hard disks), optical storage media (e.g., CD, DVD, orBlu-ray discs), or other computer readable media. For example, asillustrated in Figures, CM1 208, or modules therein, may write mappinginformation to shared data storage 500 and CM2 214, or modules therein,may read the mapping information.

FIG. 6 is a diagram illustrating providing mapping information via awireless connection according to an embodiment of the subject matterdescribed herein. In the embodiment shown in FIG. 6, CM1 208 and CM2 214may be co-located within test system 206 and may be communicativelycoupled via wireless communication modules (WCMs) 600 and 602. In someembodiments, test system 206 may include one or more hardware platformsor chassis. For example, a first processor blade may be configured asCM1 208 and a second processor blade may be configured as CM2 214. Thefirst and second processor blades may be associated with the same ordifferent hardware platforms or chassis.

In some embodiments, communications between CM1 208 and CM2 214 may befacilitated by a wireless connection, such as a Wi-Fi or Bluetoothconnection. For example, CM1 208 may include WCM 600 and CM2 214 mayinclude WCM 602. WCM 600 may receive mapping information from CM1 208,or modules therein. WCM 600 may wireless transmit mapping information toWCM 602. After receiving the mapping information, WCM 602 may providethe mapping information to CM2 214, or modules therein.

FIG. 7 is a diagram illustrating an exemplary process for providingmapping information associated with PCP in a test environment accordingto an embodiment of the subject matter described herein. In someembodiments, the exemplary process described herein, or portionsthereof, may be performed by test system 206, DUT 200, and/or anothernode or module. For example, various actions may be performed by EASM210, EPCM 212, EPCM 216, PSM 204, and/or NAT 202.

In step 700, public network addressing information may be received froma DUT 200 in response to a PCP request. For example, EPCM 212 may send arequest for public network addressing information (e.g., a public IPaddress and a port number) to PSM 204. PSM 204 may respond with thepublic network addressing information. The public network addressinginformation may be usable to send application traffic from EACM 216 toEASM 210 via NAT 202.

In step 702, mapping information is provided to EACM 216 for use insending application traffic, wherein the mapping information includesthe public network addressing information. For example, EPCM 212 maygenerate a message that include mapping information and may send theinformation to EACM 216 or another module.

In some embodiments, the mapping information includes private networkaddressing information associated with the public network addressinginformation.

In some embodiments, the emulated application client module sendsincoming application traffic associated with the public networkaddressing information to the DUT.

In some embodiments, DUT 200 is a network address translator (NAT), afirewall, a router, a proxy, a server, or a gateway.

In some embodiments, test system 206 may include EASM 210. In someembodiments, test system 206 may be distributed across multiple chassisor blades.

In some embodiments, communications may occur between portions of testsystem 206 via an internal connection (e.g., a backplane connection or amid-plane connection), an external cable connection (e.g., FireWire,SATA, E-SATA, SCSI, SAS DAS, FC and iSCSI), a wireless connection (e.g.,Wi-Fi or Bluetooth), or shared data storage (e.g., a local database or acache).

In some embodiments, DUT 200 modifies, using private network addressinginformation associated with the emulated application server module, theincoming application traffic and sends the modified application trafficto the emulated application server module.

It will be understood that various details of the subject matterdescribed herein may be changed without departing from the scope of thesubject matter described herein. Furthermore, the foregoing descriptionis for the purpose of illustration only, and not for the purpose oflimitation, as the subject matter described herein is defined by theclaims as set forth hereinafter.

What is claimed is:
 1. A method for providing mapping informationassociated with port control protocol (PCP) in a test environment, themethod comprising: at a test system including an emulated port controlprotocol (PCP) client module for requesting public network addressinginformation for an emulated application server module and an emulatedapplication client module for sending application traffic: receiving,from a device under test (DUT), the public network addressinginformation in response to a PCP request; and providing mappinginformation to the emulated application client module, wherein themapping information includes the public network addressing information.2. The method of claim 1 wherein the emulated application client modulesends application traffic associated with the public network addressinginformation to the DUT.
 3. The method of claim 2 wherein the DUT is anetwork address translator (NAT), a firewall, a router, a proxy, aserver, or a gateway.
 4. The method of claim 1 wherein the test systemincludes an emulated application server module.
 5. The method of claim 4wherein the DUT modifies, using private network addressing informationassociated with the emulated application server module, the applicationtraffic and sends the modified application traffic to the emulatedapplication server module.
 6. The method of claim 1 wherein the DUTincludes a PCP server module and a network address translator (NAT)module.
 7. The method of claim 1 wherein providing the public networkaddressing information to the emulated application client moduleincludes sending the public network addressing information via abackplane connection, a mid-plane connection, or an internal connection.8. The method of claim 1 wherein providing the public network addressinginformation to the emulated application client module includes storingthe public network addressing information in a data storage device thatis accessible by the emulated application client module.
 9. The methodof claim 1 wherein the public network addressing information includes apublic Internet protocol address and a port identifier.
 10. The methodof claim 1 wherein the mapping information includes private networkaddressing information associated with the public network addressinginformation.
 11. A system for providing mapping information associatedwith port control protocol (PCP) in a test environment, the systemcomprising: an emulated application client module configured to sendapplication traffic; and an emulated port control protocol (PCP) clientmodule configured to request public network addressing information foran emulated application server module, wherein the emulated port controlprotocol (PCP) client module is further configured to receive, from adevice under test (DUT), the public network addressing information inresponse to a PCP request, and to provide mapping information to theemulated application client module for use in sending applicationtraffic, wherein the mapping information includes the public networkaddressing information.
 12. The system of claim 10 wherein the emulatedapplication client module is configured to send application trafficassociated with the public network addressing information to the DUT.13. The system of claim 12 wherein the DUT is a network addresstranslator (NAT), a firewall, a router, a proxy, a server, or a gateway.14. The system of claim 10 wherein the test system includes an emulatedapplication server module.
 15. The system of claim 14 wherein the DUT isconfigured to modify, using private network addressing informationassociated with the emulated application server module, the applicationtraffic and sends the modified application traffic to the emulatedapplication server module.
 16. The system of claim 10 wherein the DUTincludes a PCP server module and a network address translator (NAT)module.
 17. The system of claim 10 wherein providing the public networkaddressing information to the emulated application client moduleincludes sending the public network addressing information via abackplane connection, a mid-plane connection, or an internal connection.18. The system of claim 10 wherein providing the public networkaddressing information to the emulated application client moduleincludes storing the public network addressing information in a datastorage device that is accessible by the emulated application clientmodule.
 19. The system of claim 10 wherein the public network addressinginformation includes a public Internet protocol address and a portidentifier.
 20. The system of claim 10 wherein the mapping informationincludes private network addressing information associated with thepublic network addressing information.
 21. The system of claim 10wherein the system includes one or more chassis having one or moreprocessors and memory.
 22. A non-transitory computer readable mediumcomprising computer executable instructions embodied in a computerreadable medium that when executed by a processor of a computer controlthe computer to perform steps comprising: at a testing platformincluding an emulated port control protocol (PCP) client module forrequesting public network addressing information for an emulatedapplication server module and an emulated application client module forsending application traffic: receiving, from a device under test (DUT),the public network addressing information in response to a PCP request;and providing mapping information to the emulated application clientmodule, wherein the mapping information includes the public networkaddressing information.